home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.5 KB | 34 lines | [TEXT/GEOL] |
- Item 2669441 8-Sept-88 23:37
-
- From: D0416 Futuresoft System Design, Dev
-
- To: X0118 Bell Northern Research,Comm.Sys.Dev
-
- cc: MACAPP.TECH$ MACAPP Tech
-
- Sub: Global Size Again
-
- Chris,
- I just encountered the same problem two nights ago and considered
- remapping segments as Russ suggested to you. But I then looked at
- MyApplication.map file and looked at BBRes segment and saw many procedures from
- Building Block objects that I knew I was not using. After a little more looking
- around I found that InitUDialog procedure (used to “Register” the UDialog
- building block objects) registered all possible UDialog objects like
- popUpMenus, Picture & Icon views and such. There were 14 different objects
- including TControl type as well as objects of TControl’s sub-classes. But I was
- only using 5 of these 14 TControl classes. I fixed the problem by replacing my
- call to InitUDialog with a New/FailNIL/RegisterType sequence of calls for ONLY
- the UDialog objects that I was using. The Segment Too Big message disappeared
- and the BBRes size dropped a few K bytes.
-
- The simple point my long winded babble above is saying instead of calling
- InitUDialog which fires up all kinds of objects (14 to be exact) forcing more
- references to Methods that the linker won’t strip, maybe only RegisterType the
- UDialog objects you are actually using. It worked for me, Russ does this sound
- right?
- -Take care, Ken Addison
-
-
-
-